fix(e2e): separate Podman Machine loopback listeners - #2622
Conversation
Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>
|
🌿 Preview your docs: https://nvidia-preview-pr-2622.docs.buildwithfern.com/openshell |
Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>
matthewgrossman
left a comment
There was a problem hiding this comment.
gator-agent
PR Review Status
Validation: PR #2622 is project-valid because it is a maintainer-authored, concentrated fix for validated issue #2607 covering macOS Podman Machine gateway loopback behavior, with matching driver-guide and debugging-skill updates.
Head SHA: eb77ee64c2ebc5df36e1726b4a096f563260025a
Base SHA: 85d992f768bf2152fc5b815fc4031c61eae1ac52
Merge base SHA: f383ee1038f91921e104405cd01e4150d533fdbe
Patch ID: bdb936589103f37cbb7d356b0f62788ea662bd19
Gator payload: 2
Review mode: initial
Previous reviewed SHA: none
Blocking findings:
- No blocking findings remain.
Carried findings:
- None
Non-blocking suggestions:
- None
Docs: Updated in docs/reference/sandbox-compute-drivers.mdx; no navigation change needed because the existing Reference folder already includes this page.
E2E: Applied test:e2e because the change affects Podman gateway listener/callback behavior and the Podman e2e harness.
Next state: gator:watch-pipeline
|
Label |
Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>
matthewgrossman
left a comment
There was a problem hiding this comment.
gator-agent
PR Review Status
Validation: PR #2622 remains project-valid because it is a maintainer-authored, concentrated fix for validated issue #2607 covering macOS Podman Machine gateway loopback behavior, with matching driver-guide and debugging-skill updates.
Head SHA: 7debf050bffd19d810b520867ba4f7c09ea28880
Base SHA: 85d992f768bf2152fc5b815fc4031c61eae1ac52
Merge base SHA: f383ee1038f91921e104405cd01e4150d533fdbe
Patch ID: e6e560d6d4e65571a575f5efaf76b529b42191a6
Gator payload: 2
Review mode: follow_up
Previous reviewed SHA: eb77ee64c2ebc5df36e1726b4a096f563260025a
Blocking findings:
GATOR-7debf050-01: The latest delta removed the explicit proxy bypass from the managed Podman gateway health probe, so proxied developer or CI environments can fail before the E2E command runs even when the gateway is healthy.
Carried findings:
- None
Docs: Already updated in docs/reference/sandbox-compute-drivers.mdx; no navigation change needed because the existing Reference folder already includes this page.
E2E: test:e2e remains required because the change affects Podman gateway listener/callback behavior and the Podman E2E harness.
Next state: gator:in-review
Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>
matthewgrossman
left a comment
There was a problem hiding this comment.
gator-agent
PR Review Status
Validation: PR #2622 remains project-valid because it is a maintainer-authored, concentrated fix for validated issue #2607 covering macOS Podman Machine gateway loopback behavior, with matching driver-guide and debugging-skill updates.
Head SHA: 4962e225e7834fb88a47ee0d82a125824cc92be4
Base SHA: 85d992f768bf2152fc5b815fc4031c61eae1ac52
Merge base SHA: f383ee1038f91921e104405cd01e4150d533fdbe
Patch ID: e6186410199d33f4e291dd37e98a84f9a354fc08
Gator payload: 2
Review mode: follow_up
Previous reviewed SHA: 7debf050bffd19d810b520867ba4f7c09ea28880
Blocking findings:
- No blocking findings remain.
GATOR-7debf050-01is resolved by the latest delta restoringcurl --noproxy '*'on the managed Podman gateway health probe.
Carried findings:
- None
Docs: Already updated in docs/reference/sandbox-compute-drivers.mdx; no navigation change needed because the existing Reference folder already includes this page.
E2E: test:e2e remains required because the change affects Podman gateway listener/callback behavior and the Podman E2E harness.
Next state: gator:watch-pipeline
Signed-off-by: Matthew Grossman <mgrossman@nvidia.com>
Monitoring CompletePR #2622 has been merged, so gator monitoring is complete. Head SHA: Final action: removing active |
Summary
TL;DR: Running
mise run e2e:podmanon macOS previously failed because Podman Machine routed its internal host callback to the same address and port as the main OpenShell gateway listener. The harness now gives the main gateway and Podman callbacks distinct loopback addresses, so the command can spin up the gateway and run the Podman E2E suite successfully on macOS.Related Issue
Fixes #2607
Changes
[::1]:PORT; keep native Linux on127.0.0.1:PORT.https://localhost:PORT, relying on standard macOS IPv6-first localhost resolution while preserving a valid TLS DNS name.::1.127.0.0.1:PORTwith its restricted authorization scope; do not broaden either listener to0.0.0.0.debug-openshell-clusterguidance.Testing
mise run pre-commitpassesmise run testpassescargo test -p openshell-core resolve_ssh_gatewaypassesmise run e2e:podmanpasses on macOS Podman MachineChecklist